5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
- Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-3: Data Dictionary

When Processing is Required


The data dictionary's input processes track modifications that, when they occur, require the dictionary (or selected portions of it) to be processed. By tracking situations that require processing, APPX can eliminate errors by removing the possibility that other components within APPX will access obsolete data specifications.

The following paragraphs describe conditions for which processing is required:

Domains require processing after they are added to the dictionary and whenever their specifications have been modified. Processing of domains is automatic in APPX. If a domain requires processing, all fields that reference the domain also require it. If a domain is deleted from the dictionary, any remaining fields that reference the domain must be modified and processed.

Files require processing after they are added to the dictionary and whenever their specifications are modified. Processing of files is automatic in APPX. In addition, a record/file must be processed whenever fields are added or deleted, or a field specification is modified. If a record/file is deleted from the dictionary, its associated fields are automatically deleted.

Work fields must be processed whenever a work field is added or deleted, and whenever a specification for any work field is modified. Processing of work fields is automatic in APPX. If any work field requires processing, all work fields are processed.

The Appx Designer must take care when modifying the Data Dictionary, especially when working with "live" files. Most changes made in the dictionary will require the file be restructured. This is an automatic condition which, when encountered, cannot be ignored or undone. The file will have to be restructured (see File Management). Restructuring a file can take a significant amount of time. Users will NOT be able to access the file until the file is successfully restructured.

Application Design Manual                                         "Powered by Appx Software"

56

©2006 By APPX Software, Inc. All Rights Reserved